Release 10.1A: OpenEdge Development:
Internationalizing Applications
Compiling translated applications
If you use the OpenEdge Translation Manager System to translate your application, you must connect to the appropriate translation databases in addition to any application databases. You can compile all the language editions into a single r-code file by using the
LANGUAGESoption of theCOMPILEstatement. This code example specifies the languages to be read from the appropriate translation database or databases. The translated character strings are stored in segments within the r-code:
All languages in the example list above can use the same code page, ISO8859-1. If the list included Russian, you would have to run this statement again in a separate session with
-cpinternalset to a code page that supports Russian, so the r-code would have a valid code page.If you compile r-code with
-cpinternalset to one code page and you run the r-code in a session with-cpinternalset to another code page, the two code pages must be compatible. OpenEdge must be able to convert one code page to the other. There areRCODE-INFOhandle attributes that allow you to read information about your r-code and about a session to determine if your code pages are compatible. Table 4–2 lists theRCODE-INFOhandle attributes that apply to international or localized applications. See theCOMPILEstatement andRCODE-INFOhandle entries in OpenEdge Development: Progress 4GL Reference for more information.
Because r-code compiles with the code page set by
-cpinternal, you must set the R-code Out Code Page (-cprcodeout) startup parameter to compile code with another code page. For more information on the-cprcodeoutstartup parameter, see OpenEdge Deployment: Startup Command and Parameter Reference .
|
Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |